Mobile communication terminal and card information reading device

ABSTRACT

A mobile communication terminal (the mobile station  100 ), served in a mobile communication network for performing wireless communications, comprises a transmitter-receiver  110,  a controller  120,  a user interface  130,  a data input/output terminal  140,  a magnetic writer  150,  and a magnetic stripe  160.  Control programs stored in a program ROM  122  include a program for controlling the magnetic writer such as writes or deletes various information into/from the magnetic stripe  160.  In a credit card ROM  123  are stored information on the attributes of a credit card contract concluded in advance between a user and a credit card company. The magnetic writer  150  writes credit card contract information provided from the controller  120  to the magnetic stripe  160  or deletes the credit card contract information from the magnetic stripe  160.

TECHNICAL FIELD

[0001] This invention relates to a mobile communication terminal forstoring a plurality of card information items; and a card informationreading device for reading the card information from the mobilecommunication terminal.

BACKGROUND ART

[0002] So far, credit transactions using credit cards and banktransactions using bank cards have been widely taking place. Recently, anew service has also began for settling payment using debit cards.

[0003] However, having a plurality of credit card contracts and aplurality of bank accounts requires carrying a credit card or bank cardfor respective contracts or accounts, which has been a problem of beingtroublesome for card users.

DISCLOSURE OF THE INVENTION

[0004] The present invention is made in consideration with theabove-mentioned situation and has an object of providing a mobilecommunication terminal and card information reading device for relievingcard users from carrying various cards such as credit cards and bankcards.

[0005] In order to achieve the above object, the present inventionprovides a mobile communication terminal, served in the mobilecommunication network for performing wireless communications, comprisinga memory for storing card information items for a plurality of cards andan output interface for selecting and reading out one of said cardinformation items from said memory to output the selected cardinformation item; and a card information reading device comprising areading device capable of reading codes displayed on a display device ofsaid mobile communication terminal and an analyzing device for analyzingsaid read codes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006]FIG. 1 is a block diagram showing a configuration of a mobilestation 100 used for a first embodiment of the present invention.

[0007]FIG. 2 is a perspective view of the mobile station 100 with amagnetic card 161 retracted.

[0008]FIG. 3 is a perspective view of the mobile station 100 with themagnetic stripe 160 portion of the magnetic card 161 protruded.

[0009]FIG. 4 is block diagram showing a configuration of a credittransaction system using the mobile station 100.

[0010]FIG. 5 is a diagram showing a configuration of a subscriberdatabase 331.

[0011]FIG. 6 is a data format diagram of a registered subscriberinformation file 304.

[0012]FIG. 7 is a diagram showing a configuration of a member database61.

[0013]FIG. 8 is a diagram showing a configuration of a credit database62.

[0014]FIG. 9 is a diagram showing a configuration of a prospectivecontract-renewal members file 601.

[0015]FIG. 10 is a block diagram showing a configuration of a gatewayserver 32.

[0016]FIG. 11A and FIG. 11B cooperate to form a flow diagram of thefirst half sequence of a flow diagram of operations for signing upcredit card contracts, shopping with a credit card via a mobile packetcommunication network, making changes in registered member information,canceling credit card contracts, and inquiring for credit histories.

[0017]FIG. 12A and FIG. 12B cooperate to form a flow diagram showing anoperation of the mobile station 100 and the credit transaction system insigning up credit card contracts.

[0018]FIG. 13A to FIG. 13J are diagrams showing screen images displayedon a liquid crystal display 132 of the mobile station 100 in signing upa credit card contract.

[0019]FIG. 14A and FIG. 14B cooperate to form a flow diagram showing anoperation of the mobile station 100 and the credit transaction system inshopping with a credit card function of the mobile station 100 in theshop.

[0020]FIG. 15A and FIG. 15B cooperate to form a flow diagram showing anoperation of the mobile station 100 and the credit transaction system inshopping with a credit card function of the mobile station 100 via themobile packet communication network.

[0021]FIG. 16A and FIG. 16B cooperate to form a flow diagram showing anoperation of the mobile station 100 and the credit transaction system inrenewing credit card contracts.

[0022]FIG. 17A and FIG. 17B cooperate to form a flow diagram showing anoperation of the mobile station 100 and credit transaction system inmaking changes in registered member information.

[0023]FIG. 18 is a flow diagram showing an operation of the mobilestation 100 and the credit transaction system in canceling credit cardcontracts.

[0024]FIG. 19 is a flow diagram showing a flow of an operation indisabling calling and credit card functions of the mobile station 100.

[0025]FIG. 20 is a flow diagram showing a flow of an operation ininquiring for credit histories.

[0026]FIG. 21 is a block diagram showing a configuration of a mobilestation 100 that displays bar codes indicating credit card contractinformation on its liquid crystal display 132.

[0027]FIG. 22 is a block diagram showing a configuration of CAT 40equipped with a bar-code reader.

[0028]FIG. 23 is a block diagram showing a configuration of the mobilestation 100 that transmits credit card contract information to the CAT40 a, 40 b, . . . by an infrared communication.

[0029]FIG. 24 is a block diagram showing a configuration of a CAT 40equipped with an infrared receiver and a demodulator.

[0030]FIG. 25 is a block diagram showing a configuration of a mobilestation 100 that transmits credit card contract information to the CAT40 a, 40 b, . . . by an existing data input/output terminal.

[0031]FIG. 26 is a block diagram showing a configuration of a CAT 40equipped with an input/output terminal.

BEST MODE OF CARRYING OUT THE INVENTION [1] First Embodiment 1.Configuration of the Embodiment 1-1. Configuration of Mobile Station

[0032]FIG. 1 is a block diagram showing a configuration of a mobilestation 100, a mobile communication terminal used in a first embodimentof the present invention. As shown in the figure, the mobile station 100has a transmitter-receiver 110, a control unit 120, a user interface130, a data input/output terminal 140, a magnetic writer 150, and amagnetic stripe 160.

[0033]FIG. 2 and FIG. 3 are perspective views showing the appearance ofthe mobile station 100. This mobile station 100 is equipped with amagnetic card 161 that has a card-type magnetic recording medium, amagnetic stripe 160 shown in FIG. 1 in the concrete, a cardretracting/protruding key 131, and a slot 101 for retracting orprotruding the magnetic card 161. The user operates the cardretracting/protruding key 131, thereby permitting the magnetic card 161retracted in the slot 101 as shown in the FIG. 2, or the magnetic stripe160 portion of the magnetic card 161 protruded out of the slot 101.

[0034] In FIG. 1, the transmitter-receiver 110 handles wirelesscommunications with base stations of a mobile communication networkwhich provides the mobile telephone communication service and the mobilepacket communication service.

[0035] The control unit 120 controls each of the sections of the mobilestation 100, and comprises a CPU 121, a program ROM 122, a credit cardcontract ROM 123, and a RAM 124. The operational modes in this mobilestation 100 include a calling mode for performing phone-to-phoneconversations via the mobile communication network, and a packetcommunication mode for performing packet communications via the mobilepacket communication network. Users can set a desired mode. The controlunit 120 controls each of the sections of the mobile station 100according to set state of each of these modes.

[0036] The RAM 124 is used as a work area for the CPU 121 or a user dataarea for storing such information as phone directory data.

[0037] The credit card contract ROM 123 is a memory for storing cardinformation. In the present embodiment, credit card contract informationon profiles of a credit card contract under which a user of the mobilestation 100 is with a credit card company are stored as cardinformation. These credit card contract information are card informationgiven from the credit card company to its members, the informationincluding, for example, the name of the credit card company with which auser is under contract, a URL of the server of the credit card company(as will hereinafter be described), the expiration date of the creditcard, and also information for identifying a user such as a credit-cardnumber (an identification number given to each credit card usuallyconsisting of 16-digit numerals) and the member's name. In a case wherea user of the mobile station 100 is under contract with a plurality ofcredit card companies, the credit card contract informationcorresponding to the plurality of credit cards are stored in this creditcard contract ROM 123.

[0038] This credit card contract ROM 123 is accessible only from aspecial ROM reader/writer or a private server owned by a credit cardcompany. In the case of being accessed from a special ROM reader/writerto the credit card contract ROM 123, write information to the creditcard contract ROM 123 are transmitted to the control unit 120 from theROM reader/writer connected to the data input/output terminal 140. Thecontrol unit 120, after ensuring the validity of the accessing ROMreader/writer, writes the write information into the credit cardcontract ROM 123. Also, in the case of being accessed from a privateserver to the credit card contract ROM 123, write information to thecredit card contract ROM 123 are transmitted to the control unit 120from the server via a network such as the mobile packet communicationnetwork. The control unit 120, after ensuring the validity of theaccessing server, writes the write information into the credit cardcontract ROM 123. The control unit 120, when it detects any means otherthan the above that tries to access the credit card contract ROM 123,carries out the disabling operation of the mobile station 100 itself.

[0039] The program ROM 122 stores control programs. The CPU 121 readsout these programs and carries out various types of control processes.These control programs include various programs described below as wellas programs for the calling function usually stored in a mobile stationof the existing mobile communication system.

[0040] These control programs include a document data viewing software,known as a browser. The CPU 121 reads out the browser from the programROM 122 to carry it out, which permits the acquiring of data in the HTMLform from various information providing servers connected to theinternet via, for example, a gateway server 32 shown in the FIG. 4. Thisgateway server 32 is a computer system established at a mobile packetgateway relaying/switching center for interconnecting the mobile packetcommunication network 30 and other networks such as the Internet 70. Thegateway server 32 performs protocol conversion for performingcommunications among a plurality of networks, each of which uses adifferent protocol. The acquiring of HTML data by the mobile station 100is performed by transmitting an acquisition request specifying the URLof a resource to a server providing information via this gateway server32 and completed by storing in the RAM 124 the HTML data transmitted, inresponse to the request, from the server providing the information.

[0041] In addition, these control programs include a program for storingcredit card contract information in the credit card contract ROM 123.This program also reads out, makes changes, or deletes the credit cardcontract information stored in the credit card contract ROM 123.

[0042] The control programs further include a program for controllingthe magnetic writer 150 that functions as an output interface foroutputting card information, thereby writing in or deleting from themagnetic stripe 160 the credit card contract information read out fromthe credit card contract ROM 123; and a program to transmit to amerchant's server 80C, 80D, as will hereinafter be described, the creditcard contract information that have been read out from the credit cardcontract ROM 123.

[0043] The control programs also include a program for, when the mobilestation 100 is turned on, transmitting information that includesinformation to the effect that the power is on and an identificationnumber for the mobile station 100 via a particular channel.

[0044] Also, as mentioned earlier, the control programs include aprogram, when it detects any attempt to access the credit card contractROM 123 by an unjustified means, for disabling the mobile station 100itself.

[0045] The magnetic writer 150 writes credit card contract informationgiven from the control unit 120 into the magnetic stripe 160, or deletescredit card contract information from the magnetic stripe 160.

[0046] The magnetic stripe 160 is similar to magnetic stripes widelyused for existing credit cards. Therefore, credit card contractinformation written in the magnetic stripe 160 is readable by acurrently widely-used credit authentication terminal (CAT) for readingmagnetic stripes.

[0047] This magnetic stripe 160 is provided on a card made of plasticthat is retractable in the mobile station 100, the magnetic card 161 inFIG. 3. This magnetic card 161 is retracted or protruded by the cardretracting/protruding key 131 established on the keypad of the mobilestation 100, or by a specified key operation using an existing keyboard(refer to FIG. 2 and FIG. 3). The magnetic card 161 is usually retractedinside the mobile station 100, but when doing shopping, the portion ofthe magnetic stripe 160 is protruded outside the mobile station 100. Theback side of this magnetic card 161 has a section for a user's signaturein the same way as existing credit cards.

[0048] The user interface 130 includes a liquid crystal display 132, akeypad by which users perform various input operations, and a microphoneand a speaker for users to hold conversations.

1-2. Configuration of Credit Transaction System

[0049]FIG. 4 is a block diagram showing a configuration of the credittransaction system using a mobile station 100. This credit transactionsystem comprises the mobile station 100, a mobile telephone network 20,and a mobile packet communication network 30, CATs 40 a, 40 b, . . . ,the Credit and Finance Information System (CAFIS) network 50, creditcard company's servers 60A, 60B, . . . , the Internet 70, and merchant'sservers 80C, 80D, . . . .

[0050] A user registered as credit card members carry the mobile station100. The mobile station 100 is capable of connecting to the mobiletelephone network 20 and the mobile packet communication network 30.

[0051] The mobile telephone network 20 provides general calling servicesusing mobile stations, and the mobile station 100 receives the servicesover this mobile telephone network 20. This mobile telephone network 20comprises many base stations 31 spaced out at a certain interval withincommunication areas, a switching unit for performing circuit-switching(not shown), a control unit 33 for controlling the inside of thenetwork, and communication cables (not shown).

[0052] This control unit 33 is equipped with a subscribers database 331that stores a variety of information relating to subscribers who use thecommunication services. The above-mentioned base stations 31, theswitching unit, the control unit 33, and communication cables are sharedby the mobile packet communication network 30.

[0053]FIG. 5 is a diagram showing a data format of the subscriberdatabase 331. As shown in the figure, the subscriber database 331 storesvarious types of information for each subscriber of the mobile telephonenetwork 20, that is, for each user of the mobile station 100, theinformation including the phone number of the mobile station 100 ownedby the subscriber, his/her name, sex, date of birth as well as disablinginformation that orders the disabling the mobile station 100 and itscredit card function. A disablement flag is registered in a disablinginformation cell for a user with the mobile station 100 and its creditcard function are disabled.

[0054] As shown in the FIG. 4, the mobile packet communication network30 includes a gateway server 32 in addition to the above-mentioned basestation 31, switching unit (not shown), control unit 33, andcommunication cables.

[0055] The gateway server 32 performs the inter-conversion of atransmission protocol for the mobile packet communication network 30 andthe TCP/IP, a standard communication protocol of the Internet 70. Inaddition, the gateway server 32 controls various types of messagedelivery processings performed among the mobile station 100, the creditcard company's server 60A, 60B, . . . , and the merchant's server 80C,80D, . . . .

[0056]FIG. 10 is a block diagram showing a configuration of the gatewayserver 32. This gateway server 32 has a control unit 301, a subscriberinformation manager 302, and a data delivery manager 303.

[0057] The control unit 301 controls each of the sections of the gatewayserver 32 and also functions as an interface among protocols such as toperform protocol conversion between the mobile packet communicationnetwork 30 and another network such as the Internet 70.

[0058] The control unit 301 stores encryption algorithm such as SecureSockets Layer (SSL). Performing communication with the credit cardcompany's server 60A, 60B, . . . and the merchant's server 80C, 80D, . .. using this encryption algorithm protects the communication.

[0059] The subscriber information manager 302 stores and manages aregistered subscriber information file 304 that can be obtainedreferring to the subscriber database 331 of the control unit 33. FIG. 6is a diagram showing a data format of the registered subscriberinformation file 304. As shown in the figure, for each subscriber of themobile packet communication network 30, that is, for each user of themobile station 100, the registered subscriber information file 304stores a variety of data such as the phone number of the mobile station100 owned by the subscriber, his/her name, sex, date of birth, thestorage location of data and electronic-mail messages delivered to theuser in the data delivery manager 303, and a password pre-registered bythe user.

[0060] The control unit 301 performs user authentication of a user ofthe mobile station 100 that has accessed to the gateway server 32 inorder to use the specified service. The control unit 301 of the gatewayserver 32 handles this user authentication by matching a passwordentered by the user on the mobile station 100 and the password withinthe registered subscriber information file 304.

[0061] The data delivery manager 303 relays the delivering ofelectronic-mail messages and various data among users of two or moremobile station 100; between a user of the mobile station 100 and a userof another network such as the Internet 70; between a user of the mobilestation 100 and a credit card company's server 60A, 60B, . . . ; andbetween a user of the mobile station 100 and a merchant's server 80C,80D, . . . .

[0062] To illustrate, the data delivery manager 303 receives acommunication request including the destination and the content of acommunication from a mobile station 100 or a credit card company'sserver 60A, 60B, . . . , and transmits the contents to the destination.Alternatively, the data delivery manager 303, after receiving thecommunication request, once stores the received contents, and makes anotification to the effect that the contents have been stored, to theterminal of the requested destination (for example, the mobile station100). Subsequently, upon receiving the request for obtaining thecontents, the data delivery manager 303 transmits the stored contents tothe terminal. For this purpose, the data delivery manager 303 has amemory (not shown) inside for storing the communication contentstemporarily.

[0063] This memory stores a variety of service information to betransmitted to the mobile station 100 and displayed as a menu on theliquid crystal display 132 of the mobile station 100. The serviceinformation are data in the HTML format, data for each service itemincluding the URL of a server which carries out each service.

[0064] This memory also stores information on merchants where creditcard purchases can be made over the mobile packet communication network30. The merchants information are also data in the HTML format, and datafor each merchant includes the URL of the server of each merchant. Thismerchants information are transmitted to the mobile station 100 anddisplayed on the liquid crystal display 132 of the mobile station 100.

[0065] When a user requests a particular service using the mobilestation 100, the mobile station 100 transmits a URL that is included indata for the service item to the gateway server 32, and the gatewayserver 32, based on the URL received, makes an access to the serverwhich implements the service. When a user makes a purchase with a creditcard at a certain merchant via the mobile packet communication network30, a URL written in the HTML data format is used as well.

[0066] A number of CATs 40 a, 40 b, . . . shown in FIG. 4 areestablished at merchants and cash dispenser(CD)s. The CATs 40 a, 40 b, .. . are equipped with a magnetic reader (not shown) and capable ofreading the credit card information recorded on the magnetic stripe 160of the mobile station 100. The CATs 40 a, 40 b, . . . are also equippedwith an input interface (not shown), and through this input interfacesalespersons in the shop can enter a certain information item such asthe amount of purchase. The CATs 40 a, 40 b, . . . are connected to aprivate network, the CAFIS network 50, to which the credit card contractinformation read from the magnetic stripe 160 and information such asthe amount of transaction, transaction date, and merchant with regard tothe credit card purchase are transmitted. These information given fromthe CATs 40 a, 40 b, . . . to the CAFIS network 50 will be referred toas credit information hereinafter.

[0067] The CAFIS network 50 is formed by connecting a number of CATs 40a, 40 b, . . . and credit card company's servers 60A, 60B, . . . . ThisCAFIS network 50 is a nationwide network that connects credit cardcompanies, distribution companies, and financial institutions, the CAFIScontrol center (not shown) centralizing the network.

[0068] This CAFIS network 50 transmits various credit information thatresult from such actions as shopping and cash advance with credit cardby a user, to one of the credit card company's servers 60A, 60B, . . .which provides a contract. It also transmits information on approval ordenial of the credit card use from the one of the credit card company'sservers 60A, 60B, . . . to one of the CATs 40 a, 40 b, . . . .

[0069] The server 60A, 60B, . . . is established at each credit cardcompany, and connected to the CAFIS network 50 and the Internet 70. Thiscredit card company's server 60A, 60B, . . . comprises a member database61A, 61B, . . . for storing such information as member profiles andcredit card contract information, and a credit database 62A, 62B, . . .for storing members' credit histories and payment settlementinformation.

[0070]FIG. 7 shows a data format of the member data base 61A, 61B, . . ., and FIG. 8 shows a data format of the credit database 62A, 62B, . . ..

[0071] As shown in FIG. 7, the member database 61A, 61B, . . . storesmember profiles such as each user's name, age, address, phone number,employment, and annual income, and credit card contract informationrelating to each credit card contract such as card number, expirationdate, and credit limit. These member profiles information are reportedby users at the time of signing up contracts, and changed anytime whenchanges are reported from the users. Further, these credit card contractinformation are information granted to each of the contracts by a creditcard company once the credit card membership is approved, and part ofthe information is updated every time the expiration date comes.

[0072] In addition, as shown in FIG. 8, the credit database 62A, 62B, .. . stores credit history such as transaction dates of credit purchasesand cash advances, merchants, and amount of transactions, and creditsettlement information such as amount paid for each billing cycle. Thiscredit history (the transaction dates, merchants, and amount oftransactions) are information transmitted from the CAT 40 a, 40 b, . . .and the merchant's server 80C, 80D, . . . to the credit card company'sserver 60A, 60B . . . . Then, the credit card company's server 60A, 60B,. . . totals amount of payment for each billing cycle based on theinformation on dates and amounts of transactions, and stores the totaledamount as credit settlement information.

[0073] The main functions of the credit card company's server 60A, 60B,. . . are 1) the processing of credit card contracts (includingadmission, renewal, changes, and cancellation), 2) the determination onapproval or denial of credit card contracts and purchases, 3) theaccumulation of various information on credit card contracts and creditcard transactions, 4) the settlement amounts on credit-cardtransactions, and 5) the provision of various information for members,each of which will be described below in detail.

[0074] First of all, the credit card company's server 60A, 60B, . . .pre-stores an entry screen to be transmitted to the mobile station 100for signing up a credit card contract and a change screen to betransmitted to the mobile station 100 for making changes in contracts;upon receiving a credit card contract request, an entry screencorresponding to the request is provided to the mobile station 100through the Internet 70 and the gateway server 32.

[0075] Furthermore, the credit card company's server 60A, 60B, . . .creates and stores a prospective contract-renewal members file 601A,601B, . . . . This prospective contract-renewal members file 601A, 601B,. . . stores information on members whose contract renewal isapproaching.

[0076]FIG. 9 shows a data format for the prospective contract-renewalmembers file 601A, 601B, . . . . As shown in this figure, theprospective contract-renewal members file 601A, 601B, . . . stores datasuch as each member's name, credit number, phone number, and date ofexpiration. The credit company's server 60A, 60B, . . . refers to theexpiration dates of credit card contracts stored for each member in themember database 61A in a certain cycle (for example, every 24 hours) toextract users whose contracts are about to expire (for example, withinone week) and obtains information on the extracted users from the memberdatabase 61A, 61B, . . . to be stored in the prospectivecontract-renewal members file 601A, 601B, . . . .

[0077] The second function of the credit company's server 60A, 60B, . .. is the determination as to approval or denial of credit-card contractsor transactions. The credit company's server 60A, 60B, . . . pre-storescriteria for examining approval or denial of credit card contracts,receives from the mobile station 100 the contents entered by the useraccording to the entry screen for sign-up, and examines whether or notthe credit card contract can be approved based on the entered contentsand examination criteria. As a result of the examination, if the creditcard contract is approved, credit card contract information to be storedin the magnetic stripe 160 of the mobile station 100 is generated andgiven to the mobile station 100.

[0078] In addition, when a user performs shopping with a credit card,this credit company's server 60A, 60B, . . . decides whether or not theshopping with the credit card taking place is valid by using creditinformation given from the CAT 40 a, 40 b, . . . (or from the merchant'sserver 80C, 80D, . . . ) and various information stored in the memberdatabase, 61A, 61B, . . . ; and transmits the results thereof to the CAT40 a, 40 b, . . . (or the merchant's server 80C, 80D, . . . ) as creditapproval or denial information.

[0079] Thirdly, the credit company's server 60A, 60B, . . . stores userprofiles and credit card contract information relating to the contractin the member database 61A, 61B, . . . , and data such as credit cardpurchases that have taken place are stored in the credit database 62A,62B, . . . .

[0080] Fourthly, the credit company's server 60A, 60B, . . . , via theCAFIS network 50, notifies credit payment information to a financialinstitution having a credit payment transfer account and performs atransfer of the credit payment.

[0081] Finally, the credit company's server 60A, 60B, . . . obtainsinformation desired by a user from among the information stored in themember database 61A, 61B, . . . and the credit database 62A, 62B, . . ., and provides the mobile station 100 with them through the Internet 70and the mobile packet communication network 30.

[0082] This credit company's server 60A, 60B, . . . stores an encryptedtransmission algorithm such as Secure Sockets Layer (SSL), and handlescommunication thereby with the gateway server 32 and the merchant'sserver 80C, 80D, . . . thereby protecting the contents of transmission.

[0083] The merchant's server 80C, 80D, . . . in FIG. 4 is a server whichprovides so called virtual shops that permit users to shop online. Themerchant's server 80C, 80D, . . . stores shopping screens to bedisplayed on the mobile station 100 as data in the HTML format. Theshopping screen data include information related with commercialproducts sold to the user such as the name of the products, productdescriptions, and prices.

[0084] The merchant's server 80C, 80D, . . . receives a credit cardshopping request from a user of the mobile station 100, provides ashopping screen thereto, and handles the processing related to thecredit card shopping in cooperation with one of the credit company'sserver 60A, 60B, . . . which performs a payment settlement for thecredit card shopping.

[0085] This merchant's server 80C, 80D, . . . stores an encryptedtransmission algorithm such as SSL, and handles communication therebywith the gateway server 32 and the credit company's server 60A, 60B, . .. , thereby protecting the contents of transmission.

2. Operation

[0086] Next, operations of the present embodiment will be describedbelow, classified into the following operational modes.

[0087] 1. Signing up for a credit card contract

[0088] 2-a. Shopping with credit card over the counter

[0089] 2-b. Shopping with credit card through the mobile packetcommunication network 30

[0090] 3. Renewing a credit card contract

[0091] 4. Making changes in registered member information

[0092] 5. Canceling a credit card contract

[0093] 6. Disabling a mobile station 100 and its credit function

[0094] 7. Inquiring one's own credit history

2-1. Signing Up for Credit Card Contract

[0095]FIG. 11A, FIG. 11B, FIG. 12A, and FIG. 12B are flow charts showingan operation when a user signs up for a credit card contract with amobile station 100.

[0096]FIG. 13A to 13J are diagrams of screen images displayed on theliquid crystal display 132 of the mobile station 100, and shownchronologically corresponding to the operation indicated in FIG. 11A,FIG. 11B, FIG. 12A, and FIG. 12B.

[0097] The operation in signing up for a credit card contract will bedescribed hereinafter in reference to FIG. 11A, FIG. 11B, FIG. 12A, andFIG. 12B.

[0098] Firstly, in step SP101, a user initiates a call to the gatewayserver 32 at a predetermined phone number and requests the start of acommunication in the packet communication mode.

[0099] In step SP 102, the gateway server 32, upon receiving the packetcommunication mode starting request, starts communication in the packetcommunication mode with the user at the other end, and transmits to themobile station 100 service menu screen data stored within itself.

[0100] In step SP 103, the mobile station 100 receives the service menuscreen data and displays the service menu on the liquid crystal display132. FIG. 13A is a diagram of a screen image displayed on the mobilestation 100 at this time.

[0101] In step SP 104, the user selects by a key operation a desiredservice from among the displayed service menu items. In this case, onthe screen indicated in FIG. 13A, the user moves a cursor on the“credit” to select it. Then, the mobile station 100 transmits to thegateway server 32 the selected service request, in this case, the“credit.”

[0102] In step SP105, the gateway server 32, in response to the receivedservice request, transmits to the mobile station 100 service menu screendata designating more detailed contents of the service, in this example,detailed contents regarding the “credit.”

[0103] In step SP106, the mobile station 100 receives the detailedservice menu screen data and displays the service menu on the liquidcrystal display 132. FIG. 13B is a diagram of a screen image displayedon the mobile station 100 at this time.

[0104] In step SP107, the user selects by a key operation a desiredservice from among the displayed detailed service menu items. In thiscase, on the screen indicated in FIG. 13B, the user moves a cursor onthe “credit card contract” to select it. Then, the mobile station 100transmits to the gateway server 32 the selected detailed servicerequest, in this case, “credit card contract.”

[0105] The above-mentioned service menu screen data are transmitted tothe mobile station 100 multiple times until the user finally specifies adesired service.

[0106] In step SP108, the gateway server 32 receives the detailedservice request and transmits, to the mobile station 100, password entryscreen data for the user to enter a password.

[0107] In step SP109, the mobile station 100 receives the password entryscreen data, and a password entry screen is displayed on the liquidcrystal display 132. The user enters a password pre-registered in thegateway server 32 in the password entering section of the password entryscreen.

[0108]FIG. 13C is a diagram of the password entry screen displayed onthe mobile station 100 at this time. The user enters the password in thepassword entering section and moves a cursor to select “enter”.

[0109] In step SP111, the mobile station 100 transmits the passwordinformation entered by the user to the gateway server 32. In step SP113,the gateway server 32 receives the password information.

[0110] In step SP 115, the gateway server 32 performs userauthentication by matching the password received from the mobile station100 and the password of the mobile station 100 stored in the subscriberinformation manager 302.

[0111] In step SP117, based on a result of the user authentication, itis determined whether the user is valid or not. When it is approved as avalid user by the determination in step SP117, the routine advances tostep SP119, and the gateway server 32, in response to a final servicerequest from the user (a credit card contract request), transmits to themobile station 100 next screen information to be displayed on the mobilestation 100.

[0112] On the other hand, if it is not approved as a valid user by thedetermination in step SP117, the routine proceeds to step SP121, and thegateway server 32 transmits to the mobile station 100 a service denialnotification indicating that the credit card contract request from theuser cannot be accepted.

[0113] Then, in step SP123, the mobile station 100 receives theinformation transmitted from the gateway server 32. Subsequently in FIG.12A, in step SP125, a next screen received by the mobile station 100 isdisplayed on the liquid crystal display 132. In this case, a list ofnames of credit card companies for which the user can sign up isdisplayed on the liquid crystal display 132.

[0114]FIG. 13D is a diagram of the screen displayed on the mobilestation 100 at this time. In the case of receiving the service denialnotification, the mobile station 100 displays the notification on itsliquid crystal display 132 (not shown), and the procedure ends.

[0115] In step SP126, the user selects by a key operation a desiredcredit card company from among the displayed credit card companies. Inother words, the user moves a cursor on a desired credit card company onthe screen shown in FIG. 13D to select “enter.” It is assumed hereinthat the credit card company A has been selected as an example.

[0116] In step SP127, the mobile station 100 transmits to the gatewayserver 32 the name of the selected credit card company (company A) andthe URL of the server 60A thereof.

[0117] In step SP129, the gateway server 32 receives the name of thecredit card company (company A) and its URL, and transmits a credit cardcontract request to the credit card company's server 60A based on thereceived URL.

[0118] The gateway server 32 at this time protects by SSL the contentsto be transmitted to the credit card company's server 60A. Also in thefollowing description of operations, the contents of communications areprotected by SSL when communications are performed among the gatewayserver 32, the credit card company's server 60A, 60B, . . . , and themerchant's server 80C, 80D, . . . .

[0119] In step SP131, the credit card company's server 60A receives thecredit card contract request from the gateway server 32.

[0120] In step SP133, the credit card company's server 60A sends entryscreen data for prompting the user to enter information (e.g. his/hername, age, date of birth, address, phone number, employment, annualincome, password, etc.) that are needed for the credit card contractwith the company A, out to the Internet 70 addressed to the mobilestation 100.

[0121] In step SP135, the gateway server 32 receives the entry screendata from the credit card company's server 60A and send it to the mobilestation 100.

[0122] In step SP 137, the mobile station 100 receives the entry screendata from the gateway server 32 and displays an entry screen on itsliquid crystal display 132.

[0123]FIG. 13E is a diagram of the screen displayed on the mobilestation 100 at this time.

[0124] Instep SP139, the user enters the necessary information whilereferring to the entry screen displayed on the liquid crystal display132. The entry screen is shown in FIG. 13E. The user has to entervarious items such as his/her phone number and employment in addition tothose shown in the figure such as his/her name, date of birth, andaddress; the user scrolls down the screen, thereby enabling these otheritems being displayed in sequence on the liquid crystal display 132.

[0125] In step SP 141, the mobile station 100 transmits the enteredcontents (hereinafter referred to as input information), to the gatewayserver 32. In step SP143, the gateway server 32 receives the inputinformation and transmit them to the credit card company's server 60A.Along with them, in step SP145, the gateway server 32 transmits theinput information to the credit card company's server 60A and anotification of credit card contract application receive completion tothe mobile station 100.

[0126] Then in step SP147, the mobile station 100 receives the receivecompletion notification from the gateway server 32 and display it on theliquid crystal display 132, thereby notifying the user. FIG. 13F is adiagram of the receive completion notification screen displayed on themobile station 100 at this time.

[0127] On the other hand, in step SP149, the credit card company'sserver 60A receives the input information from the gateway server 32. Instep SP151, the credit card company's server 60A determines whether toapprove or deny the credit card contract with regard to the receivedinput information by referring to the examination criteria stored withinitself.

[0128] In step SP153, if the contract is denied as a result of theexamination by the server 60A, the company A's server 60A proceeds tostep SP155 and sends out to the Internet 70 a contract denialnotification addressed to the mobile station 100.

[0129] If the contact is approved as a result of the determination instep SP153, the procedure of the company A's server 60A advances to stepSP157 for generating new credit card contract information and sends outto the Internet 70 a contract approval notification and the generatedcredit card contract information addressed to the mobile station 100.

[0130] Then, in step SP159, the credit card company's server 60A storesin the member database 61A user profiles and credit card contractinformation with regard to this contract.

[0131] In step SP161, the gateway server 32 receives the contract denialnotification or the contract approval notification and credit cardcontract information from the credit card company's server 60A, and oncestores those information inside.

[0132] In step SP163, the gateway server 32 pages the mobile station 100and transmits a notification indicating that it has received informationaddressed to the mobile station 100 from the credit card company'sserver 60A.

[0133] In step SP165, the mobile station 100 receives an informationreceive notification from the gateway server 32 and displays it on theliquid crystal display 132, thereby notifying the user. FIG. 13G is adiagram of the screen displayed on the mobile station 100 at this time.

[0134] Then, in step SP167, by a key operation by the user who has seenthe display, the mobile station 100 transmits to the gateway server 32an information acquiring request to request the acquiring of theinformation stored therein. In other words, the user selects “refer to”on the display shown in FIG. 13G, by which the information acquiringrequest is transmitted from the mobile station 100 to the gateway server32.

[0135] In step SP169, the gateway server 32 receives the informationacquiring request from the mobile station 100, and in response thereto,transmits to the mobile station 100 the contract denial notification, orthe contract approval notification and the credit card contractinformation.

[0136] In step SP171, the mobile station 100, receives the contractdenial notification, or the contract approval notification and thecredit card contract information from the gateway server 32.

[0137] In step SP173, the mobile station 100 displays the receivedcontents on its liquid crystal display 132. The mobile station 100, whenit has received the credit card contract approval notification and thecredit card contract information, stores the received credit cardcontract information in the credit card contract ROM 123.

[0138]FIG. 13H is a diagram of the screen showing the notification ofcredit card contract denial.

[0139]FIG. 13I, on the other hand, is a diagram of the screen showingthe notification of credit card contract approval. The user selects“next” on this screen, which in turn changes to the next screen (FIG.13I). FIG. 13J is a screen for confirming the contents of the creditcard contract.

[0140] As shown in FIG. 13J, on this screen, such information aredisplayed as “credit number” and “expiration date.”

[0141] The screen information shown in FIG. 13J are stored in the creditcard contract ROM 123, which can be displayed on the liquid crystaldisplay 132 by a specific operation by the user, thereby enabling theuser to confirm the contents of the credit card contract.

[0142] As described so far, the mobile station 100 owned by a user andthe credit card company's server 60A, 60B, . . . owned by a credit cardcompany conducts the processing for a credit card contract by wirelesscommunication means, thereby enabling the quick execution of theprocessing; specifically, the application for a credit card contractfrom a user to a credit card company; the notification of approval ordenial of the credit; and the provision of credit card contractinformation from the credit card company to the user.

[0143] The above-mentioned operation shown in step SP101 to step SP123in FIG. 11A and FIG. 11B is the operation mainly from the packetcommunication request to the user authentication, which is performed incommon in the first half sequence of each of the operations in using thecredit over the mobile communication network, making changes inregistered member information, canceling a credit card contract, andinquiring a credit history, as well as the above-mentioned operation ofsigning up a credit card contract.

2-2. Operation in Shopping with Credit Card

[0144] Next, an operation in shopping with credit card using a mobilestation 100 will be described.

[0145] There are two embodiments in the credit card shopping with themobile station 100.

[0146] They are a) an embodiment wherein credit card contractinformation on the magnetic stripe 160 are given to the credit cardcompany's server 60 through a CAT 40 at the shop; and b)the otherembodiment wherein credit card contract information stored in the creditcard contract ROM 123 are given to the credit card company's server 60through the mobile packet communication network 30, which will bedescribed separately hereinafter.

2-2-a. Operation in Over-the-Counter Shopping with Credit Card

[0147]FIG. 14A and FIG. 14B cooperate to form a flow diagram showing theoperation of the mobile station 100 and the credit transaction system inthe embodiment of using the magnetic stripe 160 at the shop.

[0148] First, by a predetermined operation by a user, the processing ofthe over-the-counter credit shopping begins at the mobile station 100.

[0149] In step SP201, the control unit 120 of the mobile station 100reads out all the credit card contract information stored in the creditcard contract ROM 123 to display their company names on the liquidcrystal display 132.

[0150] In step SP203, the user selects a desired credit card company bya key operation from among the displayed credit card companies. It isassumed herein that the credit card contract with credit card company Ahas been selected.

[0151] On the other hand, if the number of contracted credit cardcompanies is just one, the user may enter “OK” on the displayed creditcard company.

[0152] In step SP205, the control unit 120 of the mobile station 100gives the credit card contract information of the selected company A tothe magnetic writer 150, in turn writes the given information onto themagnetic stripe 160.

[0153] After the credit card contract information are written on themagnetic stripe 160, the magnetic card 161 becomes a protrudable state,and the control unit 120 displays the fact of being protrudable on theliquid crystal display 132. Then in step SP207, the user, havingconfirmed the protrudable state, pushes the card-retracting/protrudingkey of the mobile station 100, thereby protruding the magnetic stripe160 portion of the magnetic card 161 out of the mobile station 100.

[0154] In step SP209, a salesperson slides the magnetic stripe 160portion of the magnetic card 161 through a magnetic reader of a CAT(assumed herein as a CAT 40 b), which in turn the credit card contractinformation on the magnetic stripe 160 is read into the CAT 40 b.

[0155] In step SP211, a salesperson enters sales amount for the creditcard shopping into an input interface (not shown) of the CAT 40 b.

[0156] In step SP213, the CAT 40 b, through the CAFIS network 50,transmits to the company A's server 60A credit information including thecredit card contract information as well as the entered contents intothe CAT 40 b.

[0157] In step SP215, the credit card company's server 60A receives thecredit information from the CAT 40 b.

[0158] In step SP217, the credit card company's server 60A searches inthe member database 61A based on the received credit information, anddetermines whether or not the requested shopping with the credit card isvalid. This determination is to see if the credit card is not expired,if the credit limit is not over, if the magnetic stripe on the backsideis not disabled, or if the credit card contract itself has no effect.

[0159] When it is determined as invalid as a result of the determinationin step SP217, the processing by the company A's server 60A advances tostep SP219 and transmits to the CAT 40 b through the CAFIS network 50 anotification that the requested credit transaction has been denied (anda reason for the credit denial, if necessary).

[0160] On the other hand, when it is determined as valid as a result ofthe determination in step SP217, the processing by the company A'sserver 60A advances to step SP221, transmits to the CAT 40 b anotification that the requested credit transaction has been approved;further in step SP223, stores the credit record and payment informationwith regard to this credit card shopping transaction within the creditdatabase 62A.

[0161] In step SP225, the CAT 40 b receives the above notification fromthe credit card company's server 60A.

[0162] Then in step SP227, the CAT 40 b outputs the receivednotification onto a credit sales slip or a CAT display device (notshown). The salesperson performs a predetermined procedure following thedisplayed contents. After that, the user writes a signature identical tothat on the backside of the magnetic card 161 in the signature sectionof the credit sales slip with the sales amount written, thereby endingthe credit card shopping transaction.

[0163] At the time of completing the reading of the credit card contractinformation on the magnetic stripe 160, the user pushes the cardretracting/protruding key of the mobile station 100, and in step SP229,the magnetic card 161 is retracted inside the slot 101 of the mobilestation 100.

[0164] After the magnetic card is retracted, in step SP231, the controlunit 120 of the mobile station 100 orders the magnetic writer 150 todelete the credit card contract information of the company A stored onthe magnetic stripe 160, and the magnetic writer 150 executes that.

2-2-b. Operation in Credit Card Shopping with the Mobile PacketCommunication Network

[0165]FIG. 11A, FIG. 11B, FIG. 15A, and FIG. 15B cooperate to form aflow diagram showing the operation for shopping with a credit card usingthe mobile station 100.

[0166] The operation shown in FIG. 11A and FIG. 11B is almost same asthe sign-up for a credit card contract, but in step SP107 of FIG. 11A, auser should select “credit card shopping” as a desired service.Description for the rest of operation in FIG. 11A and FIG. 11B shall beomitted.

[0167] In step SP301 of FIG. 15A, all the merchants where the shoppingwith credit cards can be made by a user are displayed on the liquidcrystal display 132.

[0168] In step SP303, a user selects by a key operation a desiredmerchant from among the displayed merchants. It is assumed herein thatthe merchant C has been selected.

[0169] In step SP305, the mobile station 100 transmits the selectedmerchant's name (store C) and the URL of the merchant's server 80C tothe gateway server 32.

[0170] In step SP307, the gateway server 32 receives the merchant's name(store C) and the URL, and based on the received URL, transmits a creditcard shopping request to the merchant's server 80C.

[0171] In step SP309, the merchant's server 80C receives the credit cardshopping request from the gateway server 32.

[0172] In step SP311, the merchant's server 80C, in response to thereceived credit card shopping request, transmits shopping screen datastored in itself out to the Internet 70 addressed to the mobile station100.

[0173] In step SP313, the gateway server 32 receives the shopping screendata from the merchant's server 80C and transmits to the mobile station100.

[0174] In step SP315, the mobile station 100 receives the shoppingscreen data from the gateway server 32, and a shopping screen isdisplayed on the liquid crystal display 132.

[0175] In step SP317, the user selects a product to purchase referringto the shopping screen displayed on the liquid crystal display 132.

[0176] When the selecting of a product is completed, the mobile station100 reads out all the credit card contract information stored in thecredit card contract ROM 123, and the names of credit companies thereofare displayed on the liquid crystal display 132. Then in step SP319,from among the displayed credit card companies, the user selects acredit card company to be used in this credit card shopping. It isassumed herein that the credit card company B has been selected.

[0177] In step SP321, the mobile station 100 transmits information onthe selected product and its price, credit card contract informationwith the company B, the URL of the merchant's server 80C, and the URL ofthe credit company's server 60B to the gateway server 32.

[0178] In step SP323, the gateway server 32 receives these informationfrom the mobile station 100 and, after seeing its contents, transmitsthe information to the merchant's server 80C.

[0179] In step SP325, the merchant's server 80C receives the inputinformation from the gateway server 32. Then, the merchant's server 80C,among the received information, transmits the credit card contractinformation and sales amount information to the credit company's server60B.

[0180] In step SP327, the credit company's server 60B receives thesecredit information from the merchant's server 80C. In step SP329, thecredit company's server 60B retrieves the received credit information inthe member database 61B and determines whether the requested credit cardshopping is valid or not.

[0181] This determination is to check items such as if the credit cardcontract is not expired; if the credit limit is not exceeded; if themagnetic card is not disabled; or if the credit card contract itself hasno effect.

[0182] As a result of the determination in step SP329, when it isdetermined as invalid, the routine advances to step SP331, and thecredit company's server 60B transmits a notification indicating thedenial of the requested credit card shopping to the merchant's server80C.

[0183] On the other hand, as a result of the determination in stepSP329, when it is determined as valid, the process of the credit cardcompany's server 60B advances to step SP333, transmits a credit approvalnotification to the merchant's server 80C, and further stores the credithistory and payment information in the credit database 62B in stepSP335.

[0184] In step SP337, the merchant's server 80C receives thenotification from the credit card company's server 60B. Then in stepSP339, the merchant's server 80C transmits the received notification tothe gateway server 32 addressed to the mobile station 100. If thenotification is a credit approval notification, the merchant's server80C stores the product selected by the user as credit card salesinformation and performs a predetermined processing such as sending theproduct to the user.

[0185] In step SP341, the gateway server 32 receives the notificationfrom the merchant's server 80C and transmits to the mobile station 100.

[0186] In step SP343, the mobile station 100 receives the notificationfrom the gateway server 32 and displays the received contents on theliquid crystal display 132, thereby notifying the user.

2-3. Operation in Renewing the Credit Card Contract

[0187] Next, the operation in renewing a credit card contract will bedescribed.

[0188]FIG. 16A and FIG. 16B cooperate to form a flow diagram showing theoperational flow in renewing a credit card contract.

[0189] In step SP401, the credit card company's server (herein assumedas 60A) creates the prospective contract-renewal members file 601referring to the member database 60A. In step SP403, the credit cardcompany's server 60A transmits, referring to the prospectivecontract-renewal members file 601, a contract renewal advancenotification to notify the renewal of the credit card contract inadvance, out to the Internet 70, addressed to a mobile station (hereinassumed as the mobile station 100) of the user with prospective contractrenewal.

[0190] In step SP405, the gateway server 32, upon receiving the contractrenewal advance notification, pages the mobile station 100 to redirectthe above notification.

[0191] In step SP407, the mobile station 100 receives the contractrenewal advance notification from the gateway server 32 and displays thereceived notification on its liquid crystal display 132.

[0192] In step SP409, the mobile station 100, by a key operation by theuser, transmits response information in response to the displayedcontract renewal advance notification. The response informationdesignates either “will renew” or “will not renew” with regard to thecontract renewal.

[0193] In step SP411, the gateway server 32 receives the responseinformation from the mobile station 100 and transmits to the credit cardcompany's server 60A.

[0194] In step SP413, the credit card company's server 60A receives theresponse information from the gateway server 32.

[0195] In step SP415, the credit card company's server 60A, based on thereceived response information, determines whether or not the credit cardcontract with the user of the mobile station 100 can be renewed.

[0196] As a result of the determination in step SP415, if the contractis renewable, the routine advances to step SP417, and the creditcompany's server 60A generates renewed credit card contract information,the new credit card contract information being sent out to the Internet70 addressed to the mobile station 100 as well as being stored in themember database 60A.

[0197] As a result of the determination of step SP415, if the contractis not renewable, the routine advances to step SP421, and the creditcard company's server 60A deletes information on the user whose contractcannot be extended, the information being stored in the member database61A. Then in step SP423, the credit card company's server 60A sends anotification designating that the contract cannot be renewed, out to theInternet 70, addressed to the mobile station 100.

[0198] Then in step SP425, the gateway server 32 receives from thecredit card company's server 60A the renewed credit card contractinformation or the contract non-renewal notification and stores them forthe time being.

[0199] Then in step SP427, the gateway server 32 pages the mobilestation 100 and transmits a notification designating that informationaddressed to the mobile station 100 from the credit card company'sserver 60A have been received.

[0200] In step SP429, the mobile station 100 receives the informationreceive notification data from the gateway server 32 and displays themon its liquid crystal display 132, thereby notifying the user.

[0201] In step SP431, by a key operation by the user who has seen thedisplay, the mobile station 100 transmits to the gateway server 32 arequest for requesting to obtain the information stored therein.

[0202] In step SP433, the gateway server 32 receives the informationobtaining request from the mobile station 100, in response to which, thegateway server 32 transmits the after-renewed credit card contractinformation or the contract non-renewal notification stored therein tothe mobile station 100.

[0203] In step SP435, the mobile station 100 receives the renewed creditcard contract information or the no-contract-renewal notification datafrom the gateway server 32 and displays them on its liquid crystaldisplay 132.

[0204] In step SP437, the mobile station 100, when it has received therenewed credit card contract information, updates information such as anexpiration date. Alternatively, when it has received the effect ofno-contract-renewal, the credit card contract information stored in thecredit card contract ROM 123 is deleted after the expiration of a termof validity.

[0205] If the user does not respond to the credit card contract advancenotification given to the mobile station 100 even after the expirationdate, it is regarded that the user has responded “YES” to the contractrenewal; the credit card company server 60A transmits credit cardcontract information renewed at the time of the expiration to the mobilestation 100 via the gateway server, and the mobile station 100 updatesinformation such as an expiration date.

2-4. Operation in Changing the Registered Member Information

[0206] Also in the case of changing member's name and address, it ispossible to make these changes using a mobile station 100. An operationin making changes in a credit card contract will be describedhereinafter.

[0207]FIG. 11A, FIG. 11B, FIG. 17A, and FIG. 17B cooperate to form aflow diagram showing the operation, using the mobile station 100, in acredit card contract.

[0208] The operation shown in FIG. 11A and FIG. 11B is almost same asthe sign-up of a credit card contract, but in step SP107 of FIG. 11A, auser should select “change in registered member information” as adesired service. Description for the rest of the operation will beomitted.

[0209] In step SP501 of FIG. 17A, all the credit card companies withwhich the user is under contract are displayed on the liquid crystaldisplay 132.

[0210] In step SP503, the user selects by a key operation a desiredcredit card company from among the displayed credit card companies.Here, it is also possible to select all the credit card companies. It isassumed here that the credit card company A has been selected.

[0211] In step SP505, the mobile station 100 transmits the name of theselected credit card company to the gateway server 32.

[0212] In step SP509, the gateway server 32 receives the name of thecredit card company from the mobile station 100 and transmits a requestfor making changes in the registered member information toward thecredit card company's server 60A.

[0213] In step SP511, the credit card company's server 60A receives therequest for making changes in the registered member information.

[0214] In step SP513, the credit card company's server 60A sends changescreen information of the credit card contract of the company A out tothe Internet 70 addressed to the mobile station 100.

[0215] In step SP515, the gateway server 32 receives the change screeninformation from the credit card company's server 60A via the Internetand transmits the received screen information addressed to the mobilestation 100.

[0216] In step SP517, the mobile station 100 receives the change screeninformation from the gateway server 32 and displays a change screen onthe liquid crystal display 132.

[0217] In step SP519, the user enters items to change referring to thechange screen displayed on the liquid crystal display 132.

[0218] In step SP521, the mobile station 100 transmits the enteredchange items to the gateway server 32.

[0219] In step SP523, the gateway server 32 receives the changed itemsand transmit them to the credit card company's server 60A.

[0220] In step SP525, the credit card company's server 60A receives thechanged items.

[0221] In step SP527, the credit card company's server 60A changes userprofiles and attributes associated with the credit card contract storedin itself, based on the received changed items.

[0222] Once the changing processing is complete, the credit cardcompany's server 60A advances to step SP529 and sends a notification todesignate the completion of change-in-contract processing out to theInternet 70 addressed to the mobile station 100.

[0223] In step SP531, the gateway server 32 receives via the Internet 70the notification of completion to be transmitted to the mobile station100.

[0224] In step SP533, the mobile station 100 receives the notificationof completion from the gateway server 32, and in step SP535, the mobilestation 100 displays the received notification of completion on itsliquid crystal display 132.

2-5. Operation in Canceling a Credit Card Contract

[0225] It is possible to use this system also in the processing forcanceling a credit card contract. An operation in a credit card contractusing a mobile station 100 will be described hereinafter.

[0226]FIG. 11A, FIG. 11B, and FIG. 18 cooperate to form a flow diagramshowing the operation of the case where a user cancels a credit cardcontract using the mobile station 100.

[0227] The operation shown in FIG. 11A and FIG. 11B is almost same asthe sign-up for a credit card contract, but in step SP107 of FIG. 11A, auser should select “cancel a credit card contract” as a desired service.Description for the rest of the operation shall be omitted.

[0228] In step SP601 in FIG. 18, all the credit companies with which theuser is under contract are displayed on the liquid crystal display 132.

[0229] In step SP603, the user selects, from among the displayed creditcard companies, a desired credit card company by a key operation. It isassumed here that the credit card company A has been selected.

[0230] In step SP605, the mobile station 100 transmits the name of theselected credit card company to the gateway server 32.

[0231] In step SP607, the gateway server 32 receives the name of creditcard company from the mobile station 100 and transmits to the creditcard company's server 60A a request for canceling the credit cardcontract.

[0232] In step SP609, the credit card company's server 60A receives thecredit card contract canceling request from the gateway server 32.

[0233] In step SP611, the credit card company's server 60A, based on thereceived credit card contract canceling request, performs the cancelingprocessing of the credit card contract such as deleting the user profileinformation and credit card contract attributes information stored inthe member database 61A.

[0234] In step SP613, the credit card company's server 60A sends out tothe Internet 70 a notification that tells that the contract cancellationprocessing has been completed, addressed to the mobile station 100.

[0235] Instep SP615, the gateway server 32 receives the notification ofcompletion through the Internet 70, and sends it to the mobile station100.

[0236] In step SP617, the mobile station 100 receives the notificationof completion from the gateway server 32.

[0237] In step SP619, the mobile station 100 displays the receivednotification of completion on its liquid crystal display 132.

2-6. Operation in Disabling the Communication and Credit Card Functionof Mobile Station 100

[0238] In cases where a user has lost a mobile station 100 or had itstolen, it is necessary to disable the credit function in order toprevent a third person from illegal use of the mobile station 100. Anoperation of the mobile station 100 and the control unit in disablingthe credit function of the mobile station 100 will be describedhereinafter.

[0239]FIG. 19 is a flow chart showing the flow of the process by themobile station 100 and the control unit of disabling the credit cardfunction of the mobile station 100.

[0240] A user who owns the mobile station 100, in the case of losing themobile station 100, makes a contact with a common carrier who managesthe mobile telephone network 20 and the mobile packet communicationnetwork 30 by a predetermined method, and requests to disable thecalling and credit card function of the mobile station 100.

[0241] In step SP701, the communication carrier who has received theabove report, by using a specified administrative terminal, makes anaccess to the subscriber database 331 of the control unit 33, andregisters a flag that designates the disablement of communicationservice for the user and his credit card.

[0242] After this operation, the communication service by the mobilestation 100 of the subject user and its credit card function becomedisabled. In the concrete, the operation will be described hereinafter.

[0243] First in step SP703, a third person who has illegally gained themobile station 100 turns on the mobile station 100.

[0244] In step SP705, the mobile station 100 uses a particular channeland transmits dispatch information including a notification that tellsthat the power is on and the identification number of the mobile station100. The base station that includes the mobile station 100 in itscontrol area (herein assumed as the base station 32) receives thedispatch information concerning the location of the mobile station 100,the dispatch information being sent to the control unit 33.

[0245] In step SP707, the control unit 33 receives the dispatchinformation from the base station 32. Then in step SP709, the controlunit 33 makes an access to the subscriber database 331 and determinespresence or absence of the disabling information of the calling andcredit card functions of the sender, the mobile station 100.

[0246] In step SP711, the control unit 33, which has determined that thedisabling information is present, transmits through the base station 32to the mobile station 100 the effect that the calling and credit cardfunctions of the mobile station 100 are to be disabled.

[0247] In step SP713, the mobile station 100 receives an instruction ofdisabling the calling and credit card functions through the base station31.

[0248] In step SP715, the mobile station 100 performs the process fordisabling the calling and credit card functions.

[0249] In the process for disabling the calling, the operation of eachsection which operates for the calling process of the mobile station 100will be stopped. In the process for disabling the credit card function,the credit card contract information stored in the credit card contractROM 123 will be deleted.

2-7. Operation in Inquiring Credit History

[0250] Using a mobile station 100, a user can make an access to thecredit card company's server 60A, 60B, . . . to inquire various types ofinformation such as credit history and the amount of next paymentcharged to the user's bank account.

[0251]FIG. 11A, FIG. 11B, and FIG. 20 cooperate to form a flow diagramshowing an operation when a user inquires a credit history by using themobile station 100.

[0252] The operation shown in FIG. 11A and FIG. 11B is almost same asthe sign-up for a credit card contract, but in step SP107 of FIG. 11A, auser should select “credit history” as a desired service. Descriptionfor the rest of the operation shall be omitted.

[0253] In step SP801 of FIG. 20, all the credit card companies withwhich the user is under contract are shown on the liquid crystal display132.

[0254] In step SP803, the user selects by a key operation a desiredcredit card company from among the displayed credit card companies. Itis assumed here that the credit card company A has been selected.

[0255] In step SP805, the mobile station 100 transmits the name of theselected credit card company (company A) to the gateway server 32.

[0256] In step SP807, the gateway server 32 receives the name of theselected credit card (company A) from the mobile station 100 andtransmits a request for inquiring the credit history to the credit cardcompany's server 60A.

[0257] In step SP809, the credit card company's server 60A receives therequest for inquiring the credit history. In step SP811, the credit cardcompany's server 60A retrieves credit history information stored in thecredit database 62A.

[0258] In step SP813, the credit card company's server 60A transmits thecredit history information obtained as a result of the retrieval out tothe Internet 70 addressed to the mobile station 100.

[0259] In step SP815, the gateway server 32 receives the credit historyinformation via the Internet 70 and transmits the information to themobile station 100.

[0260] In step SP817, the mobile station 100 receives the credit historyinformation from the gateway server 32. In step SP819, the mobilestation 100 displays the received credit history on its liquid crystaldisplay 132.

B. Modifications B-1. Modifications in Signing Up for a Credit CardContract

[0261] In the above-mentioned description, all steps of the operation insigning up for a credit card contract are performed in one callingsession, but it is not necessarily in this way. In other words, theoperation of requesting a credit card contract from the mobile station100 to the credit card company's server 60 (i.e. from step SP101 in FIG.11A to step SP149 in FIG. 12B) and the operation of responding from thecredit card company's server 60 to the mobile station 100 (i.e. fromstep SP151 to step SP173 in FIG. 12B)can be separated.

[0262] To illustrate, cases can be envisioned such that it takes aconsiderable amount of time in the examination process of credit cardcontracts and that a partial or whole examination process beingperformed by other information processing devices or a human agent, inwhich cases, it is possible to once end the communication between themobile station 100 and the credit card companies' server 60, so that thecredit card companies' server 60 may notify the result of theexamination to the mobile station 100 at a later date.

[0263] Further, the processing at the credit card companies' server 60A,60B, . . . in making a credit card contract may only be the processingassociated with the operation of requesting a credit card contract.

[0264] For example, the procedure may end in the step SP149 of FIG. 12B,which is followed, in the case of the request for contract being denied,by a notification to that effect over a telephone to the user.Alternatively, in the case of the request being approved, a user isnotified to that effect over a telephone, so that he/she goes to theshop of the credit card company to get one's credit card contractinformation written in the mobile station 100 through an exclusive ROMreader/writer provided therein.

B-2. Modifications in Changing Registered Member Profiles

[0265] Various changes for registered member profiles can be conceivedsuch as credit limit and card class, i.e. the change from a normal-classcredit card to a gold-class card, in addition to the above-mentionedchanges in name and address. In such cases, in addition to theabove-mentioned group of steps of the operation, it will be necessary totake a step of examination by a credit card company and a step ofnotification to the mobile station 100 from the credit card company'sserver 60 of an approved change or a refused change.

B-3. Modifications in Disabling the Mobile Station 100 and Its CreditCard Function

[0266] Various timings can be conceived for the mobile station 100 totransmit the dispatch information, not being limited to the time whenpower is turned on.

[0267] For example, it can be envisioned such as the time when themobile station 100 requests a calling service or a packet communicationservice to the mobile communication network; and the time when theprocess for the credit use of the mobile station 100 is started at theshop. In other words, it may be set so that the mobile station 100transmits the information, triggered by some kind of operation by aperson who has the mobile station 100. Alternatively, the mobile station100 may transmit the information at all times or regularly while thepower is on.

[0268] Further, when the disabling information is registered at thecontrol unit 33, the control unit 33 may page the mobile station 100relating to the disablement to provide the mobile station 100 with thedisabling information. Upon receiving the disabling information, themobile station 100 transmits a receive confirmation signal, and thecontrol unit 33 receives the receive confirmation signal, therebyconfirming that the mobile station 100 has received the disablinginformation.

[0269] Further, the control unit 33, after detecting that there has beensome kind of information transmitted from the mobile station 100, maytransmit through many base stations 32 the above-mentioned disablinginformation to each base station's control area at all times orregularly. Then, the mobile station 100 that has received thetransmitted disabling information may conduct the disabling of its owncredit card function.

[0270] It is also possible for the control unit 33 to possess thedisabling information only for the calling function of the mobilestation 100, to be given to the mobile station 100. Then, the mobilestation 100 that has received the disablement-of-calling information maydetermine its credit card function is also to be disabled, performingthe disabling operation of not only its calling but also credit cardfunction.

B-4. Modifications in the Configurations of the Gateway Server 32,Credit Card Company's Sever 60, and Merchant's server 80

[0271] The credit company's server 60A, 60B, . . . and the merchant'sserver 80 maybe connected to, aside from the Internet 70, the gatewayserver 32 through a private line, or may be provided inside the mobilecommunication network.

B-5. Modifications in the Roles of the Gateway Server 32, Credit CardCompany's Sever 60, and Merchant's server 80

[0272] The functions of the gateway server 32, the credit company'sserver 60 and the merchant's server 80, are not limited to theabove-mentioned embodiments, but various embodiments can be conceived.For example, a part of functions of the merchant's server 80 and thecredit company's server 60 can be carried out by the gateway server 32.

[0273] In the first embodiment, the credit card company's server 60A,60B, . . . stores entry screen information and change screen informationused for making a credit card contract or changes, but the gatewayserver 32 instead can store those screen information. As a result, whena request for contract or changes in contract is transmitted from themobile station 100 to the gateway server 32, the gateway server 32 doesnot need to access the credit card company's server 60A, 60B, . . . toprovide entry screen information with the mobile station 100.

[0274] Further, the gateway server 32, instead of the credit cardcompany's server 60A, 60B, . . . , may conduct an examination fordetermining approval or denial of credit card contracts. In order to dothis, the gateway server 32 stores criteria for determining contractapproval or denial that are provided in advance from each of the creditcard company's servers 60A, 60B, . . . , so as to conduct examinationsbased on these criteria.

[0275] Further, the gateway server 32 may store the prospectivecontract-renewal members file 601. In this case, the gateway server 32is provided prospective contract-renewal members files 601 from thecredit card company's servers 60A, 60B, . . . , and based on the givenprospective contract-renewal members file 601, further process with themobile station 100 is carried out.

[0276] Also, in the above-mentioned embodiments, the gateway server 32once stores information from the credit card company's server 60A, 60B,. . . (i.e. credit card contract information and other notifications),and transmits information receive notifications to the mobile station100. Then, in the case of receiving a request for obtaining credit cardcontract information from the mobile station 100, the gateway server 32gives the credit card contract information to the mobile station 100.

[0277] However, it is not limited thereto. For example, when the gatewayserver 32 receives some kind of information addressed to the mobilestation 100 from the credit card company's server 60A, 60B, . . . , itis possible to give the information to the mobile station 100 withoutgiving any prior notification to the mobile station 100, or theinformation together with some kind of notification. In this case, whenthe mobile station 100 receives the information from the gateway server32, it transmits a receive confirmation signal, so that the gatewayserver 32 confirms that the mobile station 100 has received theinformation by receiving the reception confirmation signal.

[0278] Further, in the above-mentioned embodiment for the credit cardshopping through the mobile packet communication network 30, all theinput information transmitted from the mobile station 100 are receivedby the merchant's server 80 through the gateway server 32, and themerchant's server 80 transmits credit card contract information andamount-of-transaction information among the input information to thecredit card company's server 60, but it is not limited thereto.

[0279] For example, the gateway server 32 may classify contents of theinput information into a group of information addressed to the merchantserver 80 and the other group of information addressed to the creditcard company's server 60, and transmit them separately. That is, thegateway server 32 transmits the sales product information among theinput information to the merchant's server 80; and transmits the creditcard contract information and amount-of-transaction information to thecredit card company's server 60. Then, credit-approval or denialinformation from the credit card company's server 60 may be transmittedto the mobile station 100 through the merchant's server 80, or from thecredit card company's server 60 directly to the mobile station 100 andthe merchant's server 80.

[0280] Further, the gateway server 32 may store shopping screens and,upon receiving a request from the mobile station 100, provide the storedshopping screen with the mobile station 100.

B-6. Types of Contracts

[0281] In the above embodiments, the contract has been described. interms of the sign-up for credit cards, but it is not limited thereto.Various types of contracts may be envisioned such as opening bankaccounts or making loan contracts with financial institutions, makinginsurance contracts with insurance companies, or acquiring membershipwith various organizations.

B-7. Modifications in the Mobile Station 100 and the CAT 40 B-7-1. FirstModification

[0282] A mobile station 100 may provide credit card contract informationwith the CAT 40 a, 40 b, . . . by displaying bar codes that correspondto card information read out from the credit card contract ROM 123 andthat can be read optically.

[0283]FIG. 21 is a block diagram showing a configuration of a mobilestation 100 that displays bar codes indicating credit card contractinformation on the liquid crystal display 132.

[0284] This mobile station 100 comprises a transmitter-receiver 110, acontrol unit 120, a user interface 130 that has a liquid crystal display132, and a data input/output terminal 140.

[0285] Control programs stored in the program ROM 122 include a programfor generating bar code data designating credit card contractinformation.

[0286] When there is a need to display credit card contract information,the CPU 121 reads out credit card contract information from the creditcard contract ROM 123, generates bar code data designating the creditcard contract information in accordance with the bar code generatingprogram and displays the generated bar code on the liquid crystaldisplay 132.

[0287] On the other hand, the CAT 40 a, 40 b, . . . is equipped with abar-code reader and capable of reading the bar code displayed on theliquid crystal display 132 of the mobile station 100.

[0288]FIG. 22 is a block diagram showing a configuration of a CAT 40equipped with the bar-code reader.

[0289] The CAT 40 comprises, a user interface 41, a transmitter-receiver42, an output interface 43, a controller 44, and a bar-code reader 45.

[0290] The controller 44 controls each section of the CAT 40. The userinterface 41 is for a sales person to enter sales amount. The bar-codereader 45 reads the bar code displayed on the liquid crystal display 132of the mobile station 100. The transmitter-receiver 42 exchanges variousinformation with the CAFIS network 50. The output interface 43 is aprinting device of a credit sales slip.

[0291] Other configurations and operations are same as the firstembodiment.

[0292] What to be displayed on the liquid crystal display 132 is notlimited to bar codes but may be anything that can be optically read; forexample, calra code or veri code.

B-7-2. Second Modification

[0293] A mobile station 100 may provide credit card contract informationwith the CAT 40 a, 40 b, . . . by using an infrared interface that emitsinfrared rays indicating card information read out from credit cardcontract ROM 123.

[0294]FIG. 23 is a block diagram showing a configuration of the mobilestation 100 that provides credit card contract information with the CAT40 a, 40 b, . . . by infrared rays.

[0295] This mobile station 100 comprises a transmitter-receiver 110, acontrol unit 120, a user interface 130, a data input/output terminal140, a modulator 170, and an infrared emitter 180.

[0296] When there is a need to provide credit card contract informationto the CAT 40 a, 40 b, . . . , the CPU 121 reads out credit cardinformation from the credit card contract ROM 123 and gives them to themodulator 170. The modulator 170 modulates infrared ray carrier bysignal waves corresponding to the given credit card contract informationand gives the modulated infrared rays to the infrared emitter 180. Theinfrared emitter 180 emits the given infrared rays.

[0297] On the other hand, the CAT 40 a, 40 b, . . . is equipped with aninfrared receiver as well as a demodulator, by which the infrared raysemitted from the infrared emitter 180 of the mobile station 100 arereceived and demodulated so as to acquire the credit card contractinformation.

[0298]FIG. 24 is a block diagram showing a configuration of a CAT 40that is equipped with the infrared receiver and the demodulator.

[0299] The CAT 40 comprises a user interface 41, a transmitter-receiver42, an output interface 43, a controller 44, the infrared receiver 46,and the demodulator 47.

[0300] Other configurations and operations here are same as the firstembodiment.

B-7-3. Third Modification

[0301] Further, a mobile station 100 may provide credit card contractinformation with a CAT 40 a, 40 b, . . . through an existing datainput/output terminal for carrying out data input/output with anexternal device.

[0302]FIG. 25 is a block diagram showing a configuration of the mobilestation 100 where credit card contract information are given to the CAT40 a, 40 b, . . . through the existing data input/output terminal.

[0303] This mobile station 100 comprises a transmitter-receiver 110, acontrol unit 120, a user interface 130, and a data input/output terminal140.

[0304] When there is a need to give credit card contract information tothe CAT 40 a, 40 b, . . . , the CPU 121 reads out credit card contractinformation from the credit card contract ROM 123 and gives them to thedata input/output terminal 140. Subsequently, the data input/outputterminal 140 provides the given credit card information to a datainput/output terminal that is equipped with the CAT 40 a, 40 b, . . . .

[0305]FIG. 26 is a block diagram showing a configuration of a CAT 40that is equipped with the data input/output terminal.

[0306] The CAT 40 comprises a user interface 41, a transmitter-receiver42, an output interface 43, a controller 44, and the data input/outputterminal 48.

[0307] Other configurations and operations here are same as the firstembodiment.

B-7-4. Other Variations in Mobile Station 100 and CAT 40

[0308] In the above-mentioned description concerning the mobile station100 equipped with a magnetic stripe, the mobile station 100 has only onemagnetic stripe 160 to which the magnetic writer 150 writes in creditcard contract information every time credit transactions are performed.However, it is not limited thereto.

[0309] For example, it is possible to provide a plurality of magneticstripes 160 on the magnetic card 161 so that one magnetic stripecorresponds to one credit card contract information item. That is, itmeans to provide as many magnetic stripes 160 as the number of creditcard contracts.

[0310] In this case, the CAT 40 a, 40 b, . . . reads out a magneticstripe 160 in which card information of the designated credit cardcompany is stored from among a plurality of magnetic stripes 160.

[0311] Also, in cases where users carry out credit card shopping onlythrough the mobile packet communication network as mentioned above, themobile station 100 does not need to have a magnetic stripe 160. This isbecause it is possible to receive and transmit data to/from the creditcard company's server 60A, 60B, . . . only with a wireless communicationfunction in the case of the credit card shopping using the mobile packetcommunication network.

[0312] Further, in the above-mentioned description, mobile stations suchas cellular phones and PHS possess the card information of credit cards.However, the carrier side is not limited to a mobile station 100 but maybe any mobile communication terminal without a calling function, forexample, PDA.

[0313] Further, in the above-mentioned description, the CAT 40A, 40B, .. . may give its own information to the mobile station 100. For example,in the case of credit card shopping, information such as the date ofsales, merchant, sales amount that are stored in the CAT 40A, 40B, . . .may be given to a mobile station 100. By doing this, the mobile station100 can, without making an access the credit card company's server 60A,60B, . . . , accumulate its credit history based on which one is able tototal the amount of credit purchases to be drawn from one's bankaccount.

[0314] To do this, in each of the above-mentioned embodiments, the CAT40 a, 40 b, . . . may be equipped with a data input/output terminalcapable of giving the above information by being connected to the datainput/output terminal of the mobile station 100.

B-8. Variations in User Authentication

[0315] The above-mentioned embodiments are such that the gateway server32 conducts user authentication by matching the password pre-stored inthe gateway server 32 and the password entered to the mobile station 100by its user upon a request for starting a packet communication, but itis not limited thereto.

[0316] For example, the mobile station 100 may store a password for userauthentication in advance. By doing this, the mobile station 100 canconduct user authentication without carrying out communication with thegateway server 32.

[0317] Further, in addition to the password (a first password) stored inthe gateway server 32, another password (a second password) may bestored in the credit card company's server 60. In this case, uponstarting a packet communication, the first password is matched betweenthe mobile station 100 and the gateway server 32, the second passwordfurther being matched between the mobile station 100 and the credit cardcompany's server 60 at the time of shopping with credit card orinquiring for one's credit history. Thus, it is expected to enhance theprotection of privacy and security in using credit.

1. A mobile communication terminal that is served in a mobilecommunication network and performs wireless communications, comprising:a memory for storing card information items with regard to one or aplurality of cards; and an output interface for reading out from saidmemory said card information items so as to be output.
 2. A mobilecommunication terminal according to claim 1, further comprisingselecting means for selecting from said plurality of card informationitems a card information item desired by a user, wherein said outputinterface reads out from said memory the card information item selectedby said selecting means so as to be output.
 3. A mobile communicationterminal according to claim 1, wherein said card information areinformation required for electronic-commerce transactions.
 4. A mobilecommunication terminal according to claim 3, wherein said informationrequired for electronic-commerce transactions are credit cardinformation.
 5. A mobile communication terminal according to claim 1,wherein said card information includes at least information foridentifying a user.
 6. A mobile communication terminal according toclaim 1, wherein said output interface comprises: a magnetic recordingmedium; and a magnetic writer for reading out the card informationselected by said selecting means from said memory to be written intosaid magnetic recording medium
 7. A mobile communication terminalaccording to claim 6, wherein said magnetic recording medium is acard-type magnetic recording medium that can be read by a card readingdevice.
 8. A mobile communication terminal according to claim 6, whereinsaid magnetic recording medium is provided within said mobilecommunication terminal, said magnetic recording medium being retractedinside said mobile communication terminal or being protruded out of saidmobile communication terminal by a predetermined operation on saidmobile communication terminal.
 9. A mobile communication terminalaccording to claim 8, said magnetic writer, when the magnetic recordingmedium protruded out of said mobile communication terminal is retractedinside said mobile communication terminal, deletes the card informationwritten in said magnetic recording medium.
 10. A mobile communicationterminal according to claim 1, wherein said output interface comprises acode displaying device for displaying code that corresponds to cardinformation read out from said memory, the code being opticallyreadable.
 11. A mobile communication terminal according to claim 1,wherein said output interface is an infrared interface for emittinginfrared rays designating card information read out from said memory.12. A mobile communication terminal according to claim 1, wherein saidoutput interface comprises: a data input/output terminal for performingdata input/output with an external device; and a data reading device forproviding card information read out from said memory with said datainput/output terminal.
 13. A mobile communication terminal according toclaim 1, wherein said mobile communication terminal is a mobiletelephone for performing wireless telephone communications.
 14. A mobilecommunication terminal, comprising transmitting means for performingwireless communications with others through a mobile communicationnetwork; and a magnetic recording medium for storing a plurality of cardinformation items.